Internet protocol for IP private branch exchanges

ABSTRACT

An Internet protocol query for Internet protocol private branch exchanges including a private branch exchange that is connected to the public switched telephone network for receiving a call setup request, the private branch exchange not being enabled for receiving calling name delivery information from a telecommunications circuit; at least one of an incumbent local exchange carrier switch and a competitive local exchange carrier switch in communication with the private branch exchange, the at least one of the incumbent local exchange carrier switch and the competitive local exchange carrier switch having the telecommunications circuit not enabled for calling name delivery information retrieval; a network in communication with the private branch exchange; and a calling name delivery database in communication with the network for receiving calling name delivery queries from the private branch exchange based on the call setup request. Methods for routing calls based on ENUM information is also included.

FIELD OF THE INVENTION

The field of the invention relates in general to the field of Internetprotocol exchanges, in particular, to an Internet protocol query forinternet private branch exchanges.

BACKGROUND OF THE INVENTION

Conventional and Internet protocol (“IP”) private branch exchanges(“PBXs”) are typically connected to the public switched telephonenetwork (“PSTN”) through time-division multiplexing (“TDM”) integratedservices digital network (“ISDN”) primary rate interface (“PRI”)circuits. Customers typically purchase IP PBXs that have Calling NameDelivery (“CNAM”) as a feature. CNAM is a service that displays acaller's name on the calling party's digital readout on theirtelecommunications device. This is similar to the Caller ID service, butthat the calling party's name is displayed along with their callingnumber or instead of the calling number. The customer pays a fee for theservice, which can be anywhere from $50-$90 per PRI per month for theCNAM To deliver the CNAM to the IP PBX, the customer'stelecommunications provider, such as an incumbent local exchange carrier(“ILEC”) or competitive local exchange carrier (“CLEC”), may launch aCNAM query when a call is destined for the PRI trunk group. TheILEC/CLEC may then deliver the CNAM information via the signaling “D”channel on the PRI. Currently, the IP PBXs connected to the PSTN viaPRIs do not have the functionality of launching a query for CNAMinformation via IP. Typically, the ISDN PRI circuits are purchased fromthe ILEC/CLEC in an operating region and they generally provideconnectivity to the PSTN for both media and signaling traffic.

Current IP PBXs rely on the network of the ILEC/CLEC to query hosteddatabases for CNAM and other information. In a typical operation, a callsetup is attempted for an inbound call and the PRI is equipped with CNAMDelivery, so the ILEC/CLEC Class 5 switch launches a CNAM query toeither its database, or to a database provider with whom it has acontract. The database or database provider may be part of or accessedthrough a signaling transfer point (“STP”) or switching control point(“SCP”); this query may either be in IP or TDM format. Generally, thedatabase is queried based on an incoming telephone number and anassociated name is delivered to the ILEC/CLEC Class 5 switch. The Class5 switch passes the CNAM information to a PBX via the SS7 packet, forexample. At the PBX, the CNAM data is eventually delivered to theappropriate station on the customer's premise, after which the calltakes place.

Typically, the CNAM information is delivered in the SS7 transactioncapabilities access part (“TCAP”) portion of the packet along with othercall setup information, such as parameter set identifier, parameterlength, generic name, generic name length, presentation, spare,availability, type of name, and name, for example.

Telephone number mapping or electronic number mapping (“ENUM”) is asuite of protocols that unify the telephone numbering system E.164 withthe Internet addressing system domain name system (“DNS”) by usingindirect lookup method to obtain naming authority pointer (“NAPTR”)methods. ENUM resolves addressing of telephone numbers to a uniformresource locator (“URL”). If an ENUM query is launched based on theoutbound telephone number, then the response may include all URLaddresses of the devices (e.g., Instant Messaging (“IM”), fax, mobile,etc.) associated with the telephone numbers. Currently, IP PBXs mustrely on their servicing ILEC/CLEC to launch ENUM queries, if desired.Generally, ENUM is used today in voice over internet protocol (“VoIP”)Peering Exchanges and for inter-carrier multimedia messaging services(“MMS”) routing. ENUM queries launched in IP PBXs via IP connections mayprovide outbound calls to be routed by IP instead of TDM, and canprovide information necessary to support inter-carrier enhanced IPservices, such as find-me/follow-me service.

SUMMARY

In one embodiment, the present IP query for IP PBXs may be connected tothe PSTN using TDM ISDN PRI circuits that do not have the CNAM deliveryfeature activated by the ILEC/CLEC Instead of the signaling network ofthe ILEC/CLEC retrieving the CNAM information, the data is retrievedusing public or private IP. In one embodiment, a call setup is attemptedfor an inbound call. The PRI is not equipped with a CNAM delivery, thusno CNAM query is launched via the Class 5 switch; however, the IP queryfor IP PBXs switch launches a CNAM query via IP to either its CNAMdatabase, an internal CNAM database, or to a CNAM database provider withwhom it may have a contract. At this point, the call setup may besuspended via the PBX signaling TDM The query, based on the incomingcaller's telephone number, may be launched to an internal databaseinitially, and then directed to the IP address of a contracted hosteddatabase provider if no response is received initially. In one aspect,the IP address may typically be that of the database provider's SessionBorder Controller (“SBC”). A SIP SS7 protocol converter may be part ofthe database provider's system. The incoming caller's name or CNAMinformation associated with queried telephone number may be delivered tothe PBX switch and the appropriate station after which the call may takeplace. In one embodiment, the present Internet protocol query forInternet protocol private branch exchanges (“IP query for IP PBXs”)provides for PBX customers an alternative to ILEC/CLEC provided CNAMs ata cost per PRI.

The present IP query for IP PBXs may allow IP PBX customers to receiveCNAM information at a lower price than that which is typically offered.With regard to ENUM, the present IP query for IP PBXs provides IP PBXend users the ability to send queries to the network provider of theirchoice to receive ENUM information. The present IP query for IP PBXssolves the problems of overpriced CNAM delivery to IP PBXs and limitedoptions for delivery of CNAM and/or ENUM information. In one aspect, thepresent IP query for IP PBXs provides a query flow from an IP PBX switchin order to retrieve hosted database information.

By having direct access or relationships with databases and databaseproviders for CNAM and other information, they have the potential toacquire the CNAM information for a substantially less cost. IP PBXsowners may determine which incoming calls will be queried, thusproviding a greater quality of service. Additionally, queries may beinitially routed to an internal database, city/state database, or to anexternal database provider. Further, IP PBXs owners may choose public IPor may opt for a higher level of quality of service via a dedicated IPconnection for signaling traffic.

In one embodiment, the present Internet protocol query for Internetprotocol private branch exchanges includes a private branch exchangethat is connected to the public switched telephone network for receivinga call setup request, the private branch exchange not being enabled forreceiving calling name delivery information from a telecommunicationscircuit; at least one of an incumbent local exchange carrier switch anda competitive local exchange carrier switch in communication with theprivate branch exchange, the at least one of the incumbent localexchange carrier switch and the competitive local exchange carrierswitch having the telecommunications circuit not enabled for callingname delivery information retrieval; a network in communication with theprivate branch exchange; and a calling name delivery database incommunication with the network for receiving calling name deliveryqueries from the private branch exchange based on the call setuprequest.

In another embodiment, the present Internet protocol query for Internetprotocol private branch exchanges includes a private branch exchangethat is connected to at least one of a public switched telephone networkand an internet protocol network for connecting an outbound telephonecall from at least one communication device, the private branch exchangein communication with the at least one communication device; a networkin communication with the private branch exchange; and an electronicnumbering mapping database in communication with the network forreceiving electronic numbering mapping database queries from the privatebranch exchange based on a telephone number of the outbound telephonecall.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present invention are described indetail below with reference to the attached drawing figures, which areincorporated by reference herein and wherein:

FIG. 1 illustrates a block diagram of an exemplary network for IP queryfor IP PBXs according to an embodiment of the present invention;

FIG. 2 illustrates a flow chart of an exemplary process for associatingCNAM information with an incoming call according to an embodiment of thepresent invention; and

FIG. 3 illustrates a flow chart of an exemplary process for routing acall via IP to a destination according to an embodiment of the presentinvention.

DETAILED DESCRIPTION OF THE DRAWINGS

In the drawings, like or similar elements are designated with identicalreference numerals throughout the several views and figures thereof, andvarious depicted elements may not be drawn necessarily to scale.

FIG. 1 illustrates an embodiment of a network 100 for IP query for IPPBXs. In this embodiment, the network 100 may include a customer premise102 that may include one or more communication devices 104 a-104 c incommunication with a PBX 106. The customer premise 102 may furtherinclude server 120 a that may be a personal computer for performing andexecuting programs and instructions and accessing a network 132. Thecustomer premise 102 may be further in communication with an ILEC/CLECnetwork 126 that may include PRI circuits 122 in communication with thePBX 106 and a telecommunications switch 124, such as a Class 5 switch.

The network 100 may further include a database provider network 134 thatis in communication with the network 132. The database provider network134 may include a session border controller 142 and a gateway 138 incommunication with a server 120 b; the servers 120 a and 120 b(collectively 120). The database provider network 134 may furtherinclude a signaling transfer point (“STP”) 140 that may be incommunication with the servers 120 and/or gateway 138. The servers 120may be any computing devices suitable for communicating with the network132. The network 132 may be a fiber optic, cable, or telephone networkor other wired network or wireless network suitable for communicationwith the servers 120. In one embodiment, the customer premise 102 mayinclude a wireless router, adapter, switch, hub, or other suitableinterface that allows the servers 120 to communicate with the network132. The ILEC/CLEC network 126 may use a graphical user interface(“GLI”), such as website or program accessible from the servers 120 inorder to perform the features and functions herein described. In oneembodiment, the ILEC/CLEC network 126 is in communication with the PSTN144.

Additionally, the servers 120 may include processors 108 a and 108 b(108 a and 108 b collectively 108) that execute software 110 a and 110 b(110 a and 110 b collectively 110). The processors 108 may be incommunication with memories 112 a and 112 b (112 a and 112 bcollectively 112), an input/output (“I/O”) unit 114 a and 114 b (114 aand 114 b collectively 114), and storage units 116 a and 116 b (116 aand 116 b collectively 116). The storage units 116 may store databasesor data repositories 118 a-118 d thereon. The software 110 may includeinstructions for execution by the processors 108 for providing ENUM andCNAM information in accordance with the principles of the present IPquery for IP PBXs. The servers 120 may be physically located or utilizedby the customer premise 102 and database provider network 134, or anyother entity in accordance with the with the principles of the presentIP query for IP PBXs.

Each of the servers 120 may communicate via the network 132. The network132 may be the Internet, intranet, wide area networks (“WANs”), localarea networks (“LANs”), or other communication systems capable ofcommunicating information between computing devices and/or PBXs.Preferably, the network is at least one of Internet, Intranet, TDMAnetwork CDMA network PCS network GSM network, WMAX network, WLAN, datanetwork packet network, private network, PSTN, and VoIP network. Theservers 120 may communicate data packets 128 a-128 n and 130 a-130 ncontaining information related to any of the computer and networks of anentity to another one or more of the servers 120, as understood in theart. Similarly, the servers 120 may communicate information to otherservers 120 via data packets 128 a-128 n and 130 a-130 n via the network132. In addition, network 132 may be a communications network a computernetwork, an Internet network or a combination of them, and the like. Inoperation, the servers 120 may execute the software 110 to enable the IPquery for IP PBXs to acquire CNAM and ENUM information, for example.

In addition, a user may utilize host personal computers (not shown),wired communication devices (not shown), and wireless communicationsdevices (not shown) either directly with the servers 120 or indirectlyvia the network 132 or other telecommunications networks. The hostpersonal computers and wireless communications devices may enable usersof the network 100 to interface with the software 110 to display onlinemenus, catalogs, and the like to a user. Host personal computers, wiredcommunication devices, and wireless communications devices may alsoinclude other peripherals, such as keyboards, displays, microphones, andthe like. Preferably, the software 110 of the servers 120 is capable ofpresenting GUIs to their respective displays. Moreover, some or all ofthe GUIs may display CNAM and ENUM information as described herein.

The telecommunications switch 124 may communicate using a signal controlprotocol, such as a signaling system number 7 (“SS7”) protocol. The SS7protocol is used in publicly switched networks for establishingconnections between switches, performing out-of-band signaling insupport of the call-establishment, billing, routing, CNAM and/or ENUMinformation retrieval, and implementing information-exchange functionsof a PSTN. The telecommunications switch 124 may be owned and operatedby a local exchange carrier that provides standard telephone service toany number of users. In one embodiment, the telecommunications switch124 may be a Class 5 switch that is part of the network systems of thelocal carrier. However, the telecommunications switch 124 may also be aDigital Subscriber Line Access Multiplexer (“DSLAM”), Internet Protocol(“IP”) gateway, base station, or any other suitable network accesspoint.

In one embodiment, the telecommunications switch 124 may be a wire-lineswitch or public exchange using time domain multiplexing to providetelecommunications services to a particular subscriber or groups ofsubscribers. The telecommunications switch 124 may be located at a localtelephone company's central office, or at a business location serving asa PBX. The telecommunications switch 124 may provide dial-tone, callingfeatures, and additional digital and data services to subscribers, suchas communication devices 104 a-104 c. The telecommunications switch 124may also enable voice over internet protocol (“VoIP”) communication ofthe communication devices 104 a-104 a through a data network VoIP worksby sending voice information in digital form in packets, rather than inthe traditional circuit-committed protocols of the publicly switchednetwork.

The network 100 may further include any number of hardware and softwareelements that may not be shown in the example of FIG. 1. For example, inorder to facilitate VoIP communications, the communications system andtelecommunications switch 124 in particular may include applicationservers, media servers, service brokers, call agents, edge routers,gateways (signaling, trunking, access, sub, etc.), IP network serviceproviders, adapters, exchanges, switches, users, bridges, and networks.The telecommunications switch 124 or other components of a wire linenetwork such as a data, PSTN, VoIP, or other wired network may implementthe features and perform the methods herein described.

The telecommunications switch 124 may include an authentication space.The authentication space may be a partition of the server or otherstorage designated by the communications service provider. Theauthentication space may validate that a user or device, such as aclient, is allowed to authorize the telecommunications switch 124 to setpreferences, implement changes, review information, or perform otherupdates. For example, a user may be first required to provide a secureidentifier, such as a user name, password, or other authentication codeor hardware interface, to verify the user is authorized to make changeswithin the authentication space.

The authentication information may be used to create a secure connectionbetween the servers 120 and telecommunications switch 124, for example.The secure connection may be a virtual private network tunnel, anencrypted connection, firewall, or other form of secured communicationslink. The telecommunications switch 124 may use any number of gateways,proxies, applications, or interfaces for allowing the servers 120 to thetelecommunications switch 124 through the network 100. Alternatively,the servers 120 may use a wireless network or other network to accessthe telecommunications switch 124. The telecommunications switch 124 mayuse a host client application for communicating with numerous clients,for example.

The storage units 116 and/or data repositories 118 may store CNAM andENUM information as described herein. In one embodiment, the CNAMinformation may include a directory of telephone or directory numbersand related names for the telephone numbers. The numbers and names maybelong to subscribers and non-subscribers of a particular network ortelecommunications network. In one aspect, the names are associated withthe names of a particular calling party.

Additionally, the storage units 116 and/or data repositories 118 maystore ENUM information that unify the telephone numbering system E.164with the Internet addressing system DNS by using indirect lookup methodto obtain NAPTR methods. ENUM is a protocol that resolves addressing oftelephone numbers to a URL. If an ENUM query is launched based on theoutbound telephone number, then the response may include all URLaddresses of the devices, such as IM, fax, mobile, etc., associated withthe telephone numbers. ENUM is a routing technology used in VoIP PeeringExchanges and in inter-carrier MMS routing gateways. ENUM querieslaunched in IP PBXs via IP connections may provide outbound calls to berouted by IP instead of TDM In one embodiment, the ENUM is a suite ofprotocols developed to unify the telephone system with the Internet byusing E.164 addresses with DDDS and DNS. ENUM may also refer to “E164Number Mapping.” VoIP service providers may assign a URI to a customerin order to complete calls over the Internet, but ENUM may not belimited to use for VoIP service. ENUM provides a user with a domain nameon an E.164 server in order to associate a common internationaltelephone number with a URI and provide other DNS-related services. Thestorage units 116 and/or data repositories 118 may store this ENUMinformation.

In one aspect, an IP address may be associated with each differenttelephone number. In this example, a telephone number may first beassigned to a user by a carrier for service. The number may then beregistered for one or more ENUM services, such as to receive phone callsat a home or office, send emails, or send faxes. These settings that mapENUM registered services to the phone number may be stored in a namingauthority pointer (“NAPTR”) resource record located in the DNS underE164.arpa domain. A phone number may be translated into an Internetaddress as follows. Initially, using a telephone number, such as1-919-460-1234, it is initially stored as +1-919-460-1234, in E.164format with the “1” as North America's country code. Next, all thecharacters but the digits are removed, leaving “19194601234.” Then, theorder of digits is reversed and dots are placed in between each digit,such as “4.3.2.1.0.6.4.9.1.9.1.” The domain “E.164” is appended to theend, such as “4.3.2.1.0.6.4.9.1.9.1.e164.arpa.” After translating thenumber into an Internet address, ENUM may issue a DNS query on thedomain.

A database provider may determine registration of the E.164 address byassociating the address with either a globally unique service provideridentifier (“SPID”) or a pseudo-service provider identifier(“pseudo-SPID”). The pseudo-SPID may be used to identify the serviceprovider registrant of a telephone number that does not possess aglobally unique SPID in the context of industry or regulatory numbermanagement systems. A pseudo-SPID may only be applicable within thecontext of a specific ENUM service.

Further, a database provider may identify the service providerassociated with a telephone number for routing calls and messages, andoptionally mapping a telephone number to the URI associated with theservice provider. Customers may query the ENUM database through DNSqueries or through an ENUM application programming interface (“API”),such as Java. In one aspect, IP PBXs may receive software updates forperforming the functionality herein described.

In one embodiment, the PRI circuits 122 may include a circuit switch PRIor a TDM PRI circuit that includes 23 bearer channels that are 64 keach, for example. The PRI circuits 122 may further include a signalingchannel of 64 k In one aspect, the signaling link within the PRIcircuits 122 may include standard call setup information. It also mayinclude past caller ID information and any signaling that needs to takeplace between the regulars on either side of the PRI circuits 122, suchas ILEC/CLEC network 126. The bearer channels may include voice, video,and data traffic, for example.

In addition to the aforementioned aspects and embodiments, the IP queryfor IP PBXs further includes methods for associating CNAM informationand routing calls based on ENUM information. FIG. 2 illustrates anembodiment 200 of a method for CNAM inquiries with the present IP queryIP PBXs. In step 202, a call setup request may be received containing atelephone or directory number from an originating carrier to thetelecommunications switch 124 from the PSTN 144. In step 204, an IP PBX,such as PBX 106, launches an IP query for CNAM information. This stepmay include initiating a query at an internal database, such as storageunit 116 a and/or data repository 118 a or 118 b. In step 206, aninquiry is made as to whether the internal database was able to providea name or CNAM information associated with the telephone or directorynumber. If the answer to the inquiry is “yes,” then in step 214 the IPquery for IP PBXs associated CNAM is delivered to the PBX 106 and theappropriate communication device 104 a-104 c where the call is bound.

If the answer to the inquiry in step 206 is “no,” then in step 208 theIP query for IP PBXs initiates a query to an external CNAM database.This step may include suspending the call setup via the PBX 106signaling TDM. This step may also include that the IP PBX suspends callprocessing and launches an IP query via its data connection to theInternet or network 132, as described in step 210. The external databasemay be a database under contract or associated with a particulartelecommunications service provider and the like. This step may furtherinclude that the placed call that is destined for communication devices104 a-104 c and/or PBX 106 and the call setup messages are exchangedwith the serving switch and the PBX 106. As described above, the PBX 106may be in communication with the PSTN 144 using PRI circuits 122, suchas TDM ISDN PRI circuits. In this embodiment, the PRI circuits 122 donot have CNAM delivery feature activated by the telecommunicationsswitch 124. Thus, instead of the ILEC/CLEC network 126 retrieving CNAMinformation from the telecommunications switch 124, it is retrieved bythe PBX 106 and/or customer premise 102 from an external database, suchas storage units 116, and data repositories 118, or servers 120.

In step 210, the IP query for IP PBXs may launch an IP query to storageunits 116, and data repositories 118, or servers 120 via the network 132using a pre-populated IP address. This step may include that the IPquery is launched to a pre-populated IP address, thus directing thequery to the desired database provider, such as storage units 116, anddata repositories 118, or servers 120. In one aspect, the IP address maybe the IP address of the session border controller 142 of the storageunits 116, and data repositories 118, or servers 120. The IP query maybe directed over the network 132, such as the Internet via a public orprivate connection (i.e., VPN). This step may further include that thedatabase provider responds with CNAM information associated with theincoming caller's telephone number in IP format. In one embodiment, aSIP-SS7 protocol converter, such as gateway 138, may be used to convertthe telephone or directory number to an IP address as described herein.

In step 212, the system then retrieves the CNAM information from theexternal database provider. In step, 214, the retrieved CNAM informationis transmitted back to the PBX 106 for associating with the telephone ordirectory number for forwarding to the appropriate communication device104 a-104 c relating to the call setup request. The IP PBX, such as PBX106, receives the CNAM information and delivers to the appropriatestation, such as communication devices 104 a-104 c, and the call takesplace in step 216.

In one aspect, the customer premise 102 may be selective regarding theCNAM inquiries to make based on the call setup telephone numbers. Forexample, if the customer premise 102 and/or PBX 106 determine that anincoming telephone or directory number does not need CNAM information,then it may not query its internal CNAM information databases orinitiate a query through the network 132 to a database provider'snetwork such as database provider network 134. This may improve thequality of service, by providing efficient queries based ondeterminations of the customer premise 102.

FIG. 3 illustrates an embodiment 300 of a method for ENUM inquiries withthe present IP query IP PBXs. As mentioned above, ENUM information maybe used today in VoIP Peering Exchanges and for inter-carrier MMSrouting. In one embodiment, ENUM queries launched by IP PBX connections,such as PBX 106, may allow outbound calls to be routed via IP instead ofTDM if desired. In step 302, a call setup for an outbound call isrequested from the communication devices 104 a-104 c and/or PBX 106.This step may include initiating a call from the communication devices104 a-104 c by a user. In step 304, the terminating telephone ordirectory number may be used to launch an ENUM information query to aninternal database, such as storage unit 116 a and/or data repository 118a or 118 b. In step 306, an inquiry is made as to whether the internaldatabase was able to provide an ENUM information associated with thedialed telephone or directory number. This step may include retrievingan IP address associated with the dialed telephone or directory numberfrom an internal database, such as storage unit 116 a and/or datarepository 118 a or 118 b.

If the answer to the inquiry in step 306 is “yes,” then in step 312 theIP query for IP PBXs associated ENUM information is delivered to the PBX106 and the appropriate communication device 104 a-104 c. In step 312,an IP address associated with the dialed telephone or directory numberis retrieved and the call may be routed through the telecommunicationsswitch 124 via the PBX 106, for example. This step may include routingthe call through a public or private IP to the destination eitherdirectly to a VoIP provider or a Peering exchange, for example.

If the answer to the inquiry in step 306 is “no,” then in step 308 theIP query for IP PBXs initiates a query to an external ENUM database forENUM information associated with the dialed telephone or directorynumber. This step may include suspending the call setup via the PBX 106signaling TDM. This step may also include that the IP PBX suspends callprocessing and launches an IP query via its data connection to theInternet or network 132. The external database may be an ENUM databaseunder contract or associated with a particular telecommunicationsservice provider and the like.

In step 310, an inquiry is made as to whether the external database,such as database provider network 134, was able to provide an ENUMinformation associated with the dialed telephone or directory number.This step may include retrieving an IP address associated with thedialed telephone or directory number from an internal database, such asstorage unit 116 a and/or data repository 118 a or 118 b. If the answerto the inquiry in step 310 is “yes,” then in step 312 the IP query forIP PBXs associated ENUM information is delivered to the PBX 106 and theappropriate communication device 104 a-104 c. In step 312, an IP addressassociated with the dialed telephone or directory number is retrievedand the call may be routed through the network 132 via the PBX 106, forexample. This step may include routing the call through a public orprivate IP to the destination either directly to a VoIP provider or aPeering exchange, for example. In one aspect, routing calls bilaterallyto Peering partners or to Peering exchanges may be less expensive thanthrough the PSTN. Additionally, call routed to Peering partners or toPeering exchanges may be maintained in IP format, instead of convertedto TDM and back to IP. Such protocol conversions may introduce latencywhich is detrimental quality of service. In one aspect, users of the IPquery for IP PBXs may choose public IP or may opt for a higher level ofhigher level of quality of service via a dedicated IP connection, forboth IP signaling and media traffic.

If the answer to the inquiry in step 310 is “no,” then in step 314 theIP query for IP PBXs routes the call to the PSTN. In this step,appropriate signaling to the PSTN may take place as is known in the art.

In one aspect, the customer premise 102 may be selective regarding theENUM inquiries to make based on the dialed telephone number. Forexample, if the customer premise 102 and/or PBX 106 determines that thedialed telephone or directory number does not need ENUM information,then it may not query its internal ENUM information databases orinitiate a query through the network 132 to a database provider'snetwork, such as database provider network 134. This may improve thequality of service, by providing efficient queries based ondeterminations of the customer premise 102.

There has been described a system and method for distributing electronicinformation. It should be understood that the particular embodimentsdescribed within this specification are for purposes of example andshould not be construed to limit the invention. Further, it is evidentthat those skilled in the art may now make numerous uses andmodifications of the specific embodiment described, without departingfrom the inventive concepts. For example, particular additional servers,computers, networks and the like may be used to convey the informationcategories and related stored documents without departing from theinventive concepts.

What is claimed:
 1. An Internet protocol query system for Internetprotocol private branch exchanges, the system comprising: a privatebranch exchange that is connected to the public switched telephonenetwork for receiving a call setup request, the private branch exchangenot being enabled for receiving calling name delivery information from atelecommunications; circuit, wherein the private branch exchangeincludes an internal name delivery database; at least one of anincumbent local exchange carrier switch and a competitive local exchangecarrier switch in communication with the private branch exchange, the atleast one of an incumbent local exchange carrier switch and acompetitive local exchange carrier switch having the telecommunicationscircuit not enabled for calling name delivery information retrieval,wherein the internal name delivery database is independent of the atleast one of an incumbent local exchange carrier switch and acompetitive local exchange carrier switch; a network in communicationwith the private branch exchange; and an external calling name deliverydatabase, which is external to the private branch exchange and which isindependent of the at least one of an incumbent local exchange carrierswitch and a competitive local exchange carrier switch, in communicationwith the network for receiving calling name delivery queries from theprivate branch exchange based on the call setup request, wherein, inresponse to a determination that an incoming telephone number associatedwith the call setup request does not require calling name deliveryinformation, the private branch exchange is configured to withholdsending calling name delivery queries to both the internal name deliverydatabase and the external calling name delivery database.
 2. TheInternet protocol query system for Internet protocol private branchexchanges of claim 1 wherein the telecommunications circuit is a primaryrate interface circuit.
 3. The Internet protocol query system forInternet protocol private branch exchanges of claim 1 wherein thetelecommunications circuit is a time-division multiplexing integratedservices digital network primary rate interface circuit.
 4. The Internetprotocol query system for Internet protocol private branch exchanges ofclaim 1 wherein the at least one of an incumbent local exchange carrierswitch and a competitive local exchange carrier switch is a Class 5telecommunications switch.
 5. The Internet protocol query system forInternet protocol private branch exchanges of claim 1 wherein the atleast one of an incumbent local exchange carrier switch and acompetitive local exchange carrier switch is selected from the groupconsisting of Digital Subscriber Line Access Multiplexer, InternetProtocol gateway, base station, and a network access point.
 6. TheInternet protocol query system for Internet protocol private branchexchanges of claim 1 further comprising: at least one communicationsdevice in communication with the private branch exchange for receivingthe call setup information and associated calling name deliveryinformation.
 7. An Internet protocol query system for Internet protocolprivate branch exchanges, the system comprising: a private branchexchange that is connected to at least one of a public switchedtelephone network and an internet protocol network for connecting anoutbound telephone call from at least one communication device, theprivate branch exchange in communication with the at least onecommunication device, wherein the private branch exchange includes aninternal electronic numbering mapping database; a network incommunication with the private branch exchange; and an externalelectronic numbering mapping database, which is external to the privatebranch exchange, in communication with the network for receivingelectronic numbering mapping database queries from the private branchexchange based on a telephone number of the outbound telephone call,wherein the electronic numbering mapping database queries are based on asuite of protocols that unify the telephone numbering system with theInternet addressing system domain naming system, wherein, in response toa determination that the telephone number of the outbound telephone calldoes not require electronic numbering mapping information, the privatebranch exchange is configured to withhold sending electronic numberingmapping database queries to both the internal electronic numberingmapping database and the external electronic numbering mapping database.8. The Internet protocol query system for Internet protocol privatebranch exchanges of claim 7, wherein the electronic numbering mappingdatabase includes Internet protocol addresses associated with theirrespective telephone numbers.
 9. The Internet protocol query system forInternet protocol private branch exchanges of claim 7, wherein theelectronic numbering mapping database stores E.164 addresses relating tothe telephone numbers.
 10. A method for associating calling namedelivery information with an incoming telephone call comprising:receiving a call setup request including a telephone number from atleast one communications device; determining whether the telephonenumber requires calling name delivery information; in response to adetermination that the telephone number requires calling name deliveryinformation: querying an internal database, which is independent of atleast one of an incumbent local exchange carrier switch and acompetitive local exchange carrier switch, for calling name deliveryinformation related to the call setup request; querying an externaldatabase, which is independent of the at least one of an incumbent localexchange carrier switch and a competitive local exchange carrier switch,for calling name delivery information related to the call setup request,in response to a determination that the internal database is unable toprovide requested calling name delivery information; retrieving thecalling name delivery information from one of the internal database orthe external database, each of which is independent of the at least oneof an incumbent local exchange carrier switch and a competitive localexchange carrier switch; and transmitting the calling name deliveryinformation to the at least one communications device; and in responseto a determination that the telephone number does not require callingname delivery information, withholding sending calling name deliveryqueries to both the internal name delivery database and the externalcalling name delivery database.
 11. The method for associating callingname delivery information with the incoming telephone call of claim 10further comprising: suspending the call processing through a privatebranch exchange until the calling name delivery information isretrieved.
 12. The method for associating calling name deliveryinformation with an incoming telephone call of claim 10 furthercomprising: selecting those call setup request to query for calling namedelivery information.
 13. A method for routing a call comprising:receiving a call setup request including a telephone number for anoutbound call from at least one communications device; determiningwhether the telephone number requires electronic numbering mappinginformation; in response to a determination that the telephone numberrequires electronic numbering mapping information: querying an internaldatabase for electronic numbering mapping information related to thecall setup request; querying an external database via a network forelectronic numbering mapping information related to the call setuprequest, in response to a determination that the internal database isunable to provide requested electronic numbering mapping information;retrieving the electronic numbering mapping information from one of theinternal database or the external database, wherein the electronicnumbering mapping information is based on a suite of protocols thatunify the telephone numbering system with the Internet addressing systemdomain naming system; and responsive to retrieving the electronicnumbering mapping information, routing the call setup request to one ofa public switched telephone network and an Internet protocol networkbased on the retrieved electronic numbering mapping information; and inresponse to a determination that the telephone number does not requireelectronic numbering mapping information, withholding sending electronicnumbering mapping database queries to both the internal database and theexternal database.
 14. A private branch exchange for associating callingname delivery information to a call setup request comprising: a privatebranch exchange not in communication with time-division multiplexingintegrated services digital network primary rate interface circuits; aninternal calling name delivery database for associating calling namedelivery information with the call setup request, said internal callingname delivery database being communicatively coupled to the privatebranch exchange, said internal calling name delivery database beingindependent of at least one of an incumbent local exchange carrierswitch and a competitive local exchange carrier switch; and a port to anetwork for accessing an external calling name delivery database forassociating calling name delivery information with the call setuprequest, said port being communicatively coupled to the private branchexchange, wherein said external calling name delivery database isindependent of at least one of an incumbent local exchange carrierswitch and a competitive local exchange carrier switch, wherein, inresponse to a determination that an incoming telephone number associatedwith the call setup request does not require calling name deliveryinformation, the private branch exchange is configured to withholdsending calling name delivery queries to both the internal name deliverydatabase and the external calling name delivery database.
 15. A privatebranch exchange for retrieving electronic numbering mapping databaseinformation comprising: a private branch exchange not in communicationwith time-division multiplexing integrated services digital networkprimary rate interface circuits; an internal electronic numberingmapping database for receiving electronic numbering mapping queries,said internal electronic numbering mapping database beingcommunicatively coupled to the private branch exchange, wherein theelectronic numbering mapping information is based on a suite ofprotocols that unify the telephone numbering system with the Internetaddressing system domain naming system; and a port to a network foraccessing an external electronic numbering mapping database forreceiving electronic numbering mapping queries, wherein, in response toa determination that the telephone number of an outbound telephone calldoes not require electronic numbering mapping information, the privatebranch exchange is configured to withhold sending electronic numberingmapping database queries to both the internal electronic numberingmapping database and the external electronic numbering mapping database.16. The private branch exchange of claim 15, wherein the port to thenetwork for accessing the external electronic numbering mapping databaseis configured to route a call to one of public switched telephonenetwork and an Internet protocol network based on the electronicnumbering mapping information.